fix: Glibc errors#244
Merged
Merged
Conversation
daffinito
added a commit
that referenced
this pull request
Jul 10, 2025
## Task Updates * A new command line option `-ac-agents-namespace` was added for specifying a namespace for Agent Control agents ([#243](#243)). The following tasks have been updated to use the new namespace: * K8s/Resources/Config * K8s/Resources/Daemonset * K8s/Resources/Deploy * K8s/Resources/Pods ## Fixes * GLIBC related errors such as `/lib64/libc.so.6: version 'GLIBC_2.34' not found` have been resolved ([#244](#244)).
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Goals
Resolve glibc dependency issues
Implementation Details
In go 1.20, there was a change in the default value for CGO_ENABLED when it is unset. See golang/go#58550 (comment), specifically:
Setting CGO_ENABLED=0 in the build script to ensure it is disabled and we are always using pure go
How to Test
I tested with CentOS 7.9 with kernel 3.10.0-1160.119.1.el7.x86_64